Design and add a MongoDB schema (Issue 75) #100
Conversation
|
Please signoff your commits @Kannav02. If you are successful, the Example: |
Kannav02
force-pushed
the
issue-75-1
branch
2 times, most recently
from
df960a5
to
5c7de55
Compare
Signed-off-by: Kannav02 <[email protected]>
Signed-off-by: Kannav02 <[email protected]>
Signed-off-by: Kannav02 <[email protected]>
Signed-off-by: Kannav02 <[email protected]>
Signed-off-by: Kannav02 <[email protected]>
Signed-off-by: Kannav02 <[email protected]>
Signed-off-by: Kannav02 <[email protected]>
Signed-off-by: Kannav02 <[email protected]>
Signed-off-by: Kannav02 <[email protected]>
|
Hey @luarss , i believe this should be good for review now, do let me know if you want any other changes to this thank you |
|
Hi, can you please recreate the branch and PR directly from upstream and not the fork? I think there are some secrets not propagatable to forks. |
|
I am trying to push my new branch to upstream, but it says I don't have the permission to do so, I believe this is because of the write access
|
|
Do try again, given you access. |
|
I believe you were right about the secrets not being able to propagate to the fork, this is quite interesting, I can look into this as well why it is happening if you want me to, as this might lead to each contributor needing to have write access to the repo before they can merge their changes |
|
That would be helpful. Thanks! |
This PR will add the MongoDB schema to support the feedback data that was being used with google sheets
The following additions were made
.env.examplefile was made to provide an example of making MongoDB URIApart from this a minor bug fix was also done in the
frontend/utils/feedback.pyfile, which allowed the right passing of parameters to the functions during the runtime to avoid unexpected errorsAn example of when I tried to create a mongoDB instance is here , I got the collections and the database that were being created
This PR is one of many which would lead to a complete solution of issue #75